StarTeam Web Client Basics

This topic provides an overview of StarTeam Web Client.

Note: You must possess a StarTeam user license to use the StarTeam Web Client.

Capabilities

Checking files in and out.
Using public filters on the StarTeam Server to refine the scope of items to browse, but cannot create new or modify existing filters.
Creating items.
Editing item properties.
Locking and unlocking an item.
Displaying item details.
Deleting an item.
Downloading a file to a local or network drive.
Starting a view session with a generated item or folder URL.
Viewing historical revisions.
Viewing reference details.
Viewing labels.
Viewing links.
Viewing a revision's properties.
Editing a revision's comment.

StarTeam Containers

StarTeam server configurations, projects, and views are containers that allow you to organize items based on application, module, business unit, or other criteria.

The following table defines each container type and shows its icon on the StarTeam Web Client user interface.

Icon	Container	Definition
	Server Configuration	A StarTeam deployment instance, consisting of a repository and a vault. A server configuration is the highest-level StarTeam container. All files, change requests, and other items that can be interrelated and managed as a whole reside in the same server configuration.
	Project	Used to group and manage related items hierarchically in a set of folders within a StarTeam server configuration. Projects allow you to set requirements, track change requests, manage tasks, and discuss the project. Before a server configuration can be used, at least one project must be created. A server configuration can hold multiple projects, each oriented to the life-cycle needs of a specific team, application, or component.
	View	A window into a project that holds items for a specific purpose. Every new project begins with the root view, in which folders, files, and other items can be organized. Subsets of the root view's contents, called child views, can be created to support specific activities or users. For example, a project for a software product might include functional specifications, marketing requirements, source code, and test suites, all stored in separate folders in the root view. As the product progresses from one release to another, additional views of these folders can be created. One view could represent the 1.0 version of the product, while a second view represents the 2.0 version, and so on.

Icon

Container

Definition

Server Configuration

A StarTeam deployment instance, consisting of a repository and a vault. A server configuration is the highest-level StarTeam container. All files, change requests, and other items that can be interrelated and managed as a whole reside in the same server configuration.

Project

Used to group and manage related items hierarchically in a set of folders within a StarTeam server configuration. Projects allow you to set requirements, track change requests, manage tasks, and discuss the project.

Before a server configuration can be used, at least one project must be created. A server configuration can hold multiple projects, each oriented to the life-cycle needs of a specific team, application, or component.

View

A window into a project that holds items for a specific purpose. Every new project begins with the root view, in which folders, files, and other items can be organized. Subsets of the root view's contents, called child views, can be created to support specific activities or users.

For example, a project for a software product might include functional specifications, marketing requirements, source code, and test suites, all stored in separate folders in the root view. As the product progresses from one release to another, additional views of these folders can be created. One view could represent the 1.0 version of the product, while a second view represents the 2.0 version, and so on.

Supported Item Types

A typical software development life-cycle requires the development, evolution, and management of things other than source files, such as requirements, models, graphics, change requests, schedules, tests, and so on.

The following table defines each built-in item type supported by the StarTeam Web Client and shows its icon on the user interface.

Icon	Container	Definition
	File	StarTeam can store any kind of file. The StarTeam Web Client allows you to work with an existing project file in the following ways. Bulk check in and check out. View and edit file properties. View historical information about file revisions. Save a file or any of its historical revisions to a local or network drive.
	Change Request	A request to change something within the scope of a project. Development teams create change requests to record problems and enhancement requests and to track their resolution or implementation.
	Requirement	Specifies a condition the software functionality must meet. The use of requirements enables business analysts, managers, developers, QA staff, and others to perform the following activities: Organize business, user, and functional requirements in a hierarchical format Indicate the dependencies among requirements Prioritize requirements by importance Identify the impact of changes to requirements Use requirements to estimate work Identify the person creating the requirement and the person who is responsible for completing it Track the requirement lifecycle from submission to completion or rejection
	Task	Represents a needed, active, or completed unit of work. Tasks allow project team members to perform the following activities: Create new tasks and assign them to team members Review current task status Estimate hours required to complete a task Record hours spent working on a task Compare estimated to actual time spent completing a task
	Topic	The first message in a threaded conversation that serves to raise a project issue to which team members can respond. Topics and their responses allow important discussions to be documented.
	Alternate Property Editors	Alternate property editors (APE) created through StarFlow Extensions are now fully supported via the StarTeam Web Client. If APEs are enabled for the project, then the user will be shown the editor as a local dialog for updating with all workflow being fully enforced. When using APEs through the StarTeam Web Client, the APE will make a direct connection to the StarTeam Server and thus firewall settings between the user's machine and the StarTeam Server should be taken into consideration. You do not need to make changes to the code of the APE but the JAR on the server does need to be signed and re-checked in to the Starflow Extensions project. APE forms are not modal. Note: APEs cannot be closed by using the APE's "X" button. You need to use the OK or Cancel buttons. To remove the messages that the APE will show before launching: Firefox Check the option Do this automatically for files like this from now on. When the Java Dialog is displayed you will need to click Run to start the APE. Internet Explorer Check the option Do not show this again for apps from the published and location server. When the Java Dialog is displayed you will need to click Run to start the APE. Chrome Click the downloaded .JNLP file. When the Java Dialog is displayed you will need to click Run to start the APE. Check the option Do not show this again for apps from the published and location server.

StarTeam Web Client Basics

Capabilities

StarTeam Containers

Supported Item Types

Send Help Center Feedback